Data package selection for data reporting of one or more data sources

ABSTRACT

Apparatuses, methods, and systems for data source reporting are disclosed. A method includes receiving, by a network provider, data types a customer user is to have reported from one or more data sources of the customer user, wherein the reporting is from data sources, and wherein the wireless reporting is through a wireless uplink between the data sources to a base station, providing, by the network provider, options of data packages to the customer, wherein the options of data packages are selected from the set of data packages based on the data types provided by the customer user, and receiving, by the network provider, from the customer user, a selection of a data package from the provided options of data packages, wherein the selected data package includes one or more data types, and how and when data within the selected data package are to be reported.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless communications.More particularly, the described embodiments relate to systems, methodsand apparatuses for selecting a data package for data reporting of oneor more data sources.

BACKGROUND

Current data networks are designed primarily for human users and thenetwork and traffic characteristics that human users generate. Thegrowth and proliferation of low-cost embedded wireless sensors anddevices pose a new challenge of high volumes of low bandwidth devicesvying for access to limited network resources. One of the primarychallenges with these new traffic characteristics is the efficiency atwhich the shared network resources can be used. For common low bandwidthapplications such a GPS tracking, the efficiency (useful/useless dataratio) can often be below 10%. This inefficiency is the result of largevolumes of devices communicating in an uncoordinated environment.Addressing this problem is fundamental to the future commercialviability of large-scale sensor network deployments.

It is desirable to have methods, apparatuses, and systems for selectinga data package for data reporting of one or more data sources.

SUMMARY

An embodiment includes a method of data source reporting. The methodincluding receiving, by a network provider, data types a customer useris to have reported from one or more data sources of the customer user,wherein the reporting is from one or more data sources, and wherein thewireless reporting is through a wireless uplink between the one or moredata sources to a base station, providing, by the network provider,options of data packages to the customer, wherein the options of datapackages are selected from the set of data packages based on the datatypes provided by the customer user, and receiving, by the networkprovider, from the customer user, a selection of a data package from theprovided options of data packages, wherein the selected data packageincludes one or more data types, and how and when data within theselected data package are to be reported through the wireless uplink.

Another embodiment includes a wireless system. The system includes aplurality of data sources, the plurality of data sources connectedthrough a wireless link to a base station, and a network server networkconnected to the base station. The network server is operative toreceive from a customer user, data types the customer user is to havereported from one or more data sources of the customer user, wherein thereporting is from one or more data sources, and wherein the wirelessreporting is through a wireless uplink between the one or more datasources to a base station, provide options of data packages to thecustomer, wherein the options of data packages are selected from the setof data packages based on the data types provided by the customer user,and receive from the customer user, a selection of a data package fromthe provided options of data packages, wherein the selected data packageincludes one or more data types, and how and when data within theselected data package are to be reported through the wireless uplink.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a plurality of hubs that communicate data of data sourcesthrough a satellite link to a base station, according to an embodiment.

FIG. 2 shows a display of selections provided to a customer to allow thecustomer to select a data package from the provided options of datapackages, according to an embodiment.

FIG. 3 shows a network server and the determination of analytics ofnetwork reporting of data of data packages, according to an embodiment.

FIG. 4 shows an example of a selected data package, according to anembodiment.

FIG. 5 shows a network server and data bases that include similarcustomer behavior and specific characteristics of the user, according toan embodiment.

FIG. 6 is a flow chart that includes steps of a method of selecting adata package for data reporting of one or more data sources, accordingto an embodiment.

FIG. 7 shows multiple sources for providing updates or feedback of hubprofiles, according to an embodiment.

FIG. 8 shows hub profiles, according to an embodiment.

FIG. 9 shows a plurality of hubs that communicate data of data sourcesthrough a shared resource to a base station, according to an embodiment.

DETAILED DESCRIPTION

The embodiments described include methods, apparatuses, and systems forreporting data of data sources of a customer user. For an embodiment, anetwork provider receives data types a customer user is to have reportedfrom one or more data sources of the customer user. The network providerprovides options of data packages to the customer, wherein the optionsare selected from a set of data packages based on the data typesprovided by the customer user. The network provider receives from thecustomer user a selection of one or more data packages from the providedoptions of data packages, wherein the selected one or more data packagesinclude one or more data types, and how and when data within theselected one or more data packages are to be reported through thewireless uplink.

FIG. 1 shows a plurality of hubs 110 190 that communicate data of datasources through a satellite link to a base station 140, according to anembodiment. For an embodiment, a network server 170 operates to generatescheduling of the wireless communication between the base station 140and the plurality of hubs 110, 190 through wireless links 115, 116. Foran embodiment, the network server 170 may access a database 160 of, forexample, a network management element 150, aid in generating theschedule communication, and provide the scheduled communication to thebase station 140. For an embodiment, the scheduled communicationincludes allocating frequency and time slots for both uplink anddownlink wireless communication. For an embodiment, the base station 140includes a modem 145 and the hubs 110, 190 include modems 130, 132, forenabling the wireless communication between the base station 140 and thehubs 110, 190.

For an embodiment, the network server 170 bases the scheduling of thewireless communication between the base station 140 and the plurality ofhubs 110, 190 on one or more data packages selected by a customer userfrom the provided options of data packages. That is, the network server170 provides options of data packages to the customer user. The networkserver 170 then receives a data package selection from the customer user(through for example a user device 105). The options of data packagesprovided to the customer user can be adaptively updated based onconditions and performance of data reporting and the network.

For at least some embodiments, the selected data package includes one ormore data types, and how and when data within the selected data packageare to be reported through the wireless uplink. For an embodiment, thedata of data sources are reported by the hubs according to a hubprofile. For an embodiment, the hub profile includes a data packageprofile(s). For an embodiment, the data package profile(s) are based onthe data package(s) selected by the customer user.

For an embodiment, the hub profile includes a superset of informationthat contains multiple sub profiles including, the mentioned datapackage profile. For an embodiment, the hub profile includes the set ofoperating procedures that determine how data is collected, processed,and transmitted over the network.

For an embodiment, the data package profile includes a definition of howdata is organized within an over-the-air network packet. The datapackage profile may include, for example, information like the first 4bytes of this packet are temperature information. For an embodiment, thedata package profile also includes trigger functions into thisdefinition. That is, for at least some embodiments, the data packageprofile determines what (what data) is reported, and how/when the datais reported.

For an embodiment, the network server 170 generates the hub profile(121, 122, 123, 124, 125) for each of the hubs 110, 190. For example,the server 170 generates the hub profile that the base station 140provides to the hub 190. Further, for an embodiment, the network server170 generates a data package profile. For an embodiment, the datapackage profile (which as described can be included within the hubprofile) includes a periodicity, an offset (timing delay), and a carrierfrequency based on the scheduled communication. For an embodiment, thehub utilizes the periodicity, the offset, and the carrier frequency ofits hub profile for determining when and at what carrier frequency totransmit uplink wireless communication to the base station 140. Aspreviously stated, the data package selected by the customer userdetermines the reporting of data from the data sources of the customerthrough the wireless uplink. Accordingly, for an embodiment, the datapackages selected compose the data package profiles of the hubs. For anembodiment, the hub profiles and the data package profile can beutilized on a hub to hub basis, or they can be defined and managed formany hubs (thousands+) at once.

For an embodiment, the data package selections are received by thenetwork server 170 from the customer user from a user device 105 througha first network (for example, cellular) and the reporting of the data bythe hubs 110, 190 is through a second network that includes the basestation 140.

For an embodiment, the base station 140 then receives a data packageuplink wireless communication from each of the plurality of hubs 110,190 according to the hub profile and data package profile of each of thehubs 110, 190 and according to the scheduled communication. For anembodiment, the hubs 110, 190 use the data package profiles fordetermining when to transmit, and the base station 140 uses thescheduled communication to determine when to receive the uplink wirelesscommunication. That is, the data is reported 117 according to the userselected data package(s).

For an embodiment, the data sources are integrated with the hub 110,190, and as described, the data generated by these data sources isreported according to the hub profile and the data package profile. Foran embodiment, the data source (such as data sources 111, 112, 113, 114,118) are external data sources that are connected to the hubs 110, 190,and the hubs report the data received from the external data sources111, 112, 113, 114, 118 according to the hub profile and the datapackage profile. For an embodiment, the hubs 110, 190 include bothinternal (integrated with the hub) and external data sources.

As shown, for an embodiment, the uplink wireless communication istransmitted by plurality of hubs and received by the base stationthrough a satellite wireless link via a satellite 191.

FIG. 2 shows a display 200 of selections provided to a customer to allowthe customer to select a data package from the provided options of datapackages, according to an embodiment. For an embodiment, the display 200is on, for example, the user device 150 of the customer user.

For at least some embodiments, different data package options areprovided to the customer user, wherein the different data packageoptions include different pricing options $A, $B, $C. As shown, thedisplay 200 may include different data package options (Package Name 1,Package Name 2, Package Name N) which may include size, trigger, and/orcost.

Further, for at least some embodiments, the different data packagesinclude different possible reporting trigger selections, which areaccessed, for example, through a dropdown menu 210. That is, one or moretrigger functions can be selected to drive the reporting of data from ahub and data source. For example, the customer user may select fromperiodic reporting, a trigger function (that includes, for example aBoolean function), state change triggering, and/or scheduled reporting.

For at least some embodiments, the selected data package includes anidentifier, and a template, wherein the template specifies wheredifferent data types are located within the package. Preciselyspecifying where different types of data are located within the datapackage provide for efficiency in that the base station knows exactlywhere the data is located. The hubs fill the selected data package withdata as defined by the template, and the base station retrieves the datafrom the data package as defined by the template. For at least someembodiments, the template is used by the base station (or other upstreamdevice) to decode received uplink data packages and extract the data(for example, for presentation to the user) from the data packages.

As previously stated, for at least some embodiments, the selected datapackage further includes a trigger function that specifies how and whendata within the selected data package is reported through the wirelessuplink. For an embodiment, the trigger function includes one or more ofperiodic reporting, state change detection reporting, or scheduledreporting of the collected data. Again, the template includes thetrigger functions. The trigger function can be communicated to the hubsthrough the data package profiles.

For at least some embodiments, the trigger functions are weighted. Asdescribed, different data packages will have different triggerfunctions. For at least some embodiments, the different triggerfunctions have different weights. That is, the satisfaction(transmission) of one package takes priority over another data packagedepending on the trigger functions of the packages. For an embodiment,the customer user can select a weighting of the trigger functions usedto report the data from the data sources through the hubs. For example,the customer user can select period reporting and state change detectionreporting, wherein one reporting type takes priority over the other.That is, for an embodiment, the data package profiles include triggerfunction priority information.

For an embodiment, the customer user can select whether the selecteddata package profile requires an explicit reception acknowledgment fromthe base station, which if not received triggers additionaltransmissions of the data package by the hub. This option can beselected for data with high reliability requirements.

At least some embodiments include queueing the data packages based onthe trigger functions. For an embodiment, the priority informationaffects which local queue on the hub the data package is placed in. Foran embodiment, the hubs include multiple priority-based queues which areserviced by the modem (in the hub) in priority descending order. For anembodiment, data package profiles which include an explicitacknowledgment requirement (as selectable by the customer user) from thebase station the data package remains in the queue after transmissionuntil the acknowledgement is received by the hub.

For an embodiment, trigger functions can be activated by direct userinput as selected by the user in defining the data package profiles.

For an embodiment, a trigger function can be activated via a mechanicalbutton, a software button, or other user activated inputs to transmitfor example an SOS data package corresponding with an SOS data packageprofile

For at least some embodiments, the priorities of the trigger functionsare adaptively updated over at least one of time, location, geography,and/or proximity to another device, person, or object. That is, for anembodiment, the trigger functions also contain a timing selection. Forexample, a trigger function may specify that a data package must be sentwithin 1 hr of creation of the data package. An adaptive priority couldspecify a temporal priority (such as, a higher priority at night). Anadaptive priority could specify a geographical priority (geo-mappingboundaries for high priority areas—useful for the military, near hostilearea). Further, an adaptive priority could specify moving geo-mappingboundaries, such a proximity to an object, place, or person, such as adrone. The adaptive characteristics of the priorities of the triggerfunction can be selected by the user customer at the time the usercustomer is making data package selections. Further, the adaptiveupdating of the trigger function can be customer user selected. That is,the customer user may select trigger functions of the data reporting tobe adaptively weighted based on time, a location of the data source,and/or the proximity of the data source to a device, object, or person.

FIG. 3 shows a network server and the determination of analytics ofnetwork reporting of data of data packages, according to an embodiment.For at least some embodiments, data is collected at various locationswithin the network for monitoring performance of the reporting of data.For an embodiment, the data packages offered to the customer user areadaptively updated based on the analytics that are generated based on atleast the collected data. For an embodiment, the network is monitored byanalytics that report of the performance of the network. The result ofthe reports is then used to drive the package suggestion to the user, inorder to optimize or improve the network efficiency. For an embodiment,data is collected (for example by the base station) on the performanceof the network. For an embodiment, analytics are then run on this datato report of the performance levels. The performance may include, forexample utilizing ‘quiet’ hours to send data depending upon triggerfunctions. Examples of collected data include Data Connection Set UpSuccess Rate, Data Delivery Rate, Data Delivery Latency, Network AttachSuccess Rate % of Active hubs, Total Number of Channels operational,Network Utilization—are they under or over utilized, No of Channelsutilized >80%—Above 80% is a very busy channel, so will need balancingif this goes on long term, Network Uptime, Network Congestion(Blocking). FIG. 3 shows sensors of the network performance 305.However, network performance analytics may or may not use actual sensorsof the network performance. The network performance can be collected byany means available.

FIG. 4 shows an example of a selected data package profile, whichincludes the details of what data should be included in the selecteddata package according to an embodiment. For an embodiment, the datapackage profile includes, a trigger functions 410, a package identifier420, a timestamp 430 and data (data 1 440, data2 450, data N 460). Thedata package includes the package identifier 420, one or more timestamps430, and the data (data 1 440, data2 450, data N 460).

For an embodiment, the package identifier 420 is used by an upstreamdevice (such as, the base station) to determine the formatting of thedata package, which allows the upstream device to extract, translate,and consume the data from the data package, and identify thetransmitting hub of the data package.

As previously stated, the selected data package provides a template ofwhere different types of data (data 1 440, data2 450, data N 460) arelocated within the reported data package. For an embodiment, the packageidentifier functions as the template. Further, for an embodiment, one ormore time stamps 430 that are correlated with the data, is containedwithin the data package.

FIG. 5 shows a network server 170 and databases that include similarcustomer behavior and specific characteristics of the user, according toan embodiment. For an embodiment, a similar customer behavior database506 is available to the network server 170. The similar customerbehavior database 506 includes data reporting characteristics andbehaviors of similar types of customers which can be used by the networkserver 170 in providing options of data packages to the customer. Thatis, for an embodiment, the network server 170 provides options of thedata packages to the customer, wherein the options of data packages arebased on behavior of similar types of customers (industry standards).

For an embodiment, data types (and/or data type selections) received byother customer users are used to identify other customer users that aresimilar to the present customer user. Further, once similar othercustomers have been identified, the network server operates to identifythe preferences of the similar other customers, and the network serveroperates to identify what was successful for the similar othercustomers. For an embodiment, the network server operates to gatherstatistical information about what other packages have been created andprovided value for other customers, and uses that information to providesuggestions of data packages to the user.

For an embodiment, a specific customer behavior database 507 isavailable to the network server 170. For an embodiment, the networkserver 170 provides options of the data packages to the customer areadditionally based on specific characteristics of the user. For anembodiment, the specific characteristics include, for example, the datatype, the industry of a business of the customer user, the number ofhubs used by the customer user, the location of hubs, the use cases forthe hubs (what type of assets, and how are those assets (for exampletrucks used for long distance, or refrigeration, or big hauling) used).

FIG. 6 is a flow chart that includes steps of a method of selecting adata package for data reporting of one or more data sources, accordingto an embodiment. A first step 610 includes receiving, by a networkprovider, data types a customer user is to have reported from one ormore data sources of the customer user, wherein the reporting is fromone or more data sources, and wherein the wireless reporting is througha wireless uplink between the one or more data sources to a basestation. A second step 620 includes providing, by the network provider,options of data packages to the customer, wherein the options of datapackages are selected from the set of data packages based on the datatypes provided by the customer user. As described, for at least someembodiments, the options are generated based upon the customer userselected sensors connected to the hub, the specific types of dataselected, the profile of the customer user and the field of service orindustry, the current and past network operating conditions, andregulatory requirements (for an embodiment data package profiles areprovided to the customer for ease of use to satisfy regulatoryrequirements. A third step 630 includes receiving, by the networkprovider, from the customer user, a selection of one or more datapackages from the provided options of data packages, wherein theselected one or more data package includes one or more data types, andhow and when data of the selected data package are to be reportedthrough the wireless uplink. For at least some embodiments, thetransmission of data packages is scheduled, coordinated, prioritized,and controlled by a network server to reduce overhead, eliminatecollisions, and increase communication channel density via thedescriptors provided in a data package profile(s) of the selected datapackage(s).

As previously described, an embodiment includes reporting data from thedata sources of the customer through the wireless uplink according tothe selected data package. A previously described, triggering of thedata reporting is included within a data package profile. For anembodiment, the data package profile is included within the hub profile.For an embodiment, the hub profile is propagated to the hubs, andprovides information to the hub to allow the hub to report data in datapackage as specified by a customer user.

At least some embodiments further include collecting, by the networkprovider, statistics of reporting of data of data packages, andadaptively updating the options of the data packages provided to thecustomer based on the collected statistics. For a least someembodiments, the options of data packages provided to the customer areadditionally selected from the set of data packages sizes to improvedata traffic between the one or more data sources and the base station.

For an embodiment, the selected data package includes an identifier, anda template, wherein the template specifies where different data typesare located within the package. For at least some embodiments, theselected data package further includes a trigger function that specifieshow and when data within the selected data package is reported throughthe wireless uplink. For at least some embodiments, the trigger functionincludes one or more of periodic reporting, state change detectionreporting, or scheduled reporting of the collected data. For at leastsome embodiments, the trigger functions are weighted.

For at least some embodiments, providing options of data packages to thecustomer, wherein the options of data packages are selected from the setof data packages sizes, is additionally based on behavior of similartypes of customers (industry standards). At least some embodimentsinclude providing options of data packages to the customer, wherein theoptions of data packages are selected from the set of data packagessizes, is additionally based on specific characteristics of the user.For at least some embodiments, selected options of the data package areprovided to the one or more data sources through hub profiles that aregenerated by the network provider and provided to the one or more datasource through the base station.

FIG. 7 shows multiple sources for providing updates or feedback of hubprofiles, according to an embodiment. As described, for an embodiment,the network management element manages the hub profiles 121, 122, 123,124, 125 of the data devices 111, 112, 113, 114, 118. At least someembodiments include adjusting the hub profile. At least one embodimentincludes the hub profile adjustment 764 by sourced by a downstreamdevice, such as, one or more of the hubs 110, 190. At least one otherembodiment includes the hub profile adjustment 762 being sourced by, forexample, a network operation center 770 through, for example, thenetwork server.

As stated, for at least some embodiments, the hub profiles areadaptively updated based on a top down feedback from the networkoperation center 770 or the network management element 150. For anembodiment, this includes rebalancing preamble codes assigned todifferent data devices to smooth RACH (random access channel) profiles,which is triggered, for example, by the detection of excess (greaterthan a threshold amount) collisions between RACH transmission. For anembodiment, the rebalancing includes assigning to the offending devicesdisparate orthogonal preamble codes to mitigate the collisions. For anembodiment, this includes adjusting timing offsets (adjusting the timingoffset includes adjusting the relative timing of periodic reporting) tosmooth network traffic congestion and maintain network utilization forperiodic data below X %, by measuring allocated versus free networkresource units. For an embodiment, this includes updating hub profileswhen changing an application of a data device, triggered by user/owneroperator intervention, for example, via a web console. For anembodiment, this includes updating the course round trip delay timing,triggered, for example, by a new hub registration on a base station.

As stated, for at least some embodiments, the hub profiles areadaptively updated based on a bottom up feedback from the hubs 110, 190or the data sources 111, 112, 113, 114, 118. For an embodiment, thisincludes the previously described fine round-trip timing delay,constantly updated within the hub profiles based upon GPS coordinates ofthe hubs 110, 190. For an embodiment, this includes the hub profile of adata device being updated by a hub through a communication link to thehub. For example, a user/operator may proactively update a profilethrough the hub by connecting via wireless phone to the hub. This can beuseful, for example, when the hub is located in a remote location thatis not serviced by a cellular network, and therefore, a user/operatorhas no way of connecting to the network operation center 770 or thenetwork management element 150 without the wireless satellite connectionprovided by the hub. The only way for the user/operator to update one ormore of the hub profiles is through the bottom up feedback provided bythe hub.

FIG. 8 shows hub profiles, according to an embodiment. The hub profilesprovide coordination of the communication of the data of the datadevices over the shared wireless satellite links. The communication caninclude one or more of real time data reporting, scheduled datareporting, and/or periodic data reporting. The hub profile for a givendata device provides the hub associated with the data device the abilityto control a timing of communication of the data for each of the one ormore data sources from the hub to a base station through the wirelesssatellite link. The controlled timing provides for synchronization ofthe communication of the data with respect to the communication of dataof other data source of both the same hub, and for one or more differenthubs. For an embodiment, the hub profile additionally provides the hubwith a frequency allocation for the communication of the data of thedata source.

An exemplary generic hub profile 810 of FIG. 8 includes enablement ofreal time access or real time reporting of the data of the data device,enablement of scheduled access or scheduled reporting of the data of thedata device, and enablement of periodic access or periodic reporting ofthe data of the data device. As previously described, for an embodiment,the data included within the reported data packages is placed within thedata packages according to a template within the data package profile.Further, for an embodiment, the hub profile also includes an estimatedMCS (modulation and coding scheme). Further, for an embodiment, the hubprofile also includes a data processing function.

A specific example of a hub profile 820 provides for reporting of thelocation of a data device. This could be, for example, the reporting ofdata of a data device associated with a vehicle. For this embodiment,both the real time data reporting and the periodic data reporting areenabled, but the scheduled reporting is not enabled. As previouslystated, for an embodiment, the reporting of the data is specified by thetemplate within the data package profile, and reported according to thetrigger function of the data package profile, which may be customer userselected. As shown, for the specific case of the hub profile 820, theperiodic reporting is specified to report once every 15 minutes,beginning and 12:00 (noon). Further, the reporting data package includesa message size of 16 bytes, wherein the preamble codes and the MCS arespecified. The hub profile 820 includes a specific data processingfunction. The exemplary function includes determining whether the datadevice (and therefore, the vehicle associated with the data device) iswithin a geographical fence. While the data device is within thegeographical fence, the data device follows the periodic reportingschedule as specified by the hub profile. If the data device is detectedto leave an area specified by the geographical fence, the real timereporting flag is triggered, and the hub of the data device performedreal time communication with the base station that includes, forexample, the location of the data device as detected outside of thegeographical fence.

FIG. 9 shows a plurality of hubs that communicate data of data sourcesthrough a shared resource to a base station, according to an embodiment.As shown, the data sources 911, 912, 913, 914, 915 are connected to thehubs 910, 990. The hubs 910, 990 communicate through modems 930, 932 toa modem 945 of the base station 940 through the wireless links. For anembodiment, the wireless links are a shared resource 999 that has alimited capacity. The described embodiments include hub profiles whichare utilized to provide efficient use of the shared resource 999.

For an embodiment, the base station 940 also communicates with thenetwork server 970. As previously described, data package selections maybe received by the network server 970 from a user customer. Further,trigger functions for reporting of data of the data packages may bereceived by the network server 970 from the customer user, which isincluded within the data package profile, which is include within thehub profiles.

As previously described, it is to be understood that the data sources911, 912, 913, 914, 915 can vary in type, and can each require verydifferent data reporting characteristics. The shared resource 999 is alimited resource, and the use of this limited resource should bejudicious and efficient. In order to efficiently utilize the sharedresource 999, each of the data sources 911, 912, 913, 914, 915 areprovided with hub profiles 921, 922, 923, 924, 925 (including thecorresponding data package profile) that coordinate the timing (and/orfrequency) of reporting (communication by the hubs 910, 990 to the basestation 940 through the shared resource 999) of the data provided by thedata sources 911, 912, 913, 914, 915.

For an embodiment, a network management element 950 maintains a database960 in which the hub profiles 921, 922, 923, 924, 925 can be stored andmaintained. Further, the network management element 950 manages the hubprofiles 921, 922, 923, 924, 925, wherein the management includesensuring that synchronization is maintained during the data reporting bythe hubs 910, 990 of the data of each of the data sources 911, 912, 913,914, 915. That is, the data reported by each hub 910, 990 of the data ofthe data sources 911, 912, 913, 914, 915 maintains synchronization ofthe data reporting of each of the data sources 911, 912, 913, 914, 915relative to each other. Again, the network management element 950ensures this synchronization through management of the hub profiles 921,922, 923, 924, 925. The synchronization between the data sources 911,912, 913, 914, 915 distributes the timing of the reporting of the dataof each of the data sources 911, 912, 913, 914, 915 to prevent thereporting of one device from interfering with the reporting of anotherdevice, and provides for efficiency in the data reporting.

For at least some embodiments, the network management element 950resides in a central network location perhaps collocated with multiplebase stations and/or co-located with a network operations center (asshown, for example, in FIG. 6). For an embodiment, the networkmanagement element 950 directly communicates with the base station 940and initiates the transfer of hub profiles across the network via thebase station 940 to the hubs 910, 990.

For at least some embodiments, hub profiles are distributed when newhubs are brought onto the network, when hubs change ownership, or whenthe hubs are re-provisioned. Other changes to hub profile contentsoutside of these situations are more likely addressed by sync packets(for an embodiment, a sync packet is a packet to update the value of aspecific field inside of a hub profile, but not necessarily updating thestructure of the hub profile) were only small changes to profile fieldsare required.

As described, the hub profiles 921, 922, 923, 924, 925 control timing ofwhen the hubs 910, 990 communicate the data of the data sources 911,912, 913, 914, 915 through the shared resource 999. Accordingly, thedescribed embodiments coordinate access to the shared resource 999 toensure optimal usage of the network resource to avoid collisions betweenpackets, the transmission of redundant information, and to reshapeundesired traffic profiles.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated. The described embodiments are toonly be limited by the claims.

What is claimed:
 1. A method, comprising: receiving, by a networkprovider, data types a customer user is to have wirelessly reported fromone or more data sources of the customer user, wherein the wirelessreporting is from one or more data sources, and wherein the wirelessreporting is through a wireless uplink between the one or more datasources to a base station; providing, by the network provider, optionsof data packages to the customer, wherein the options of data packagesare selected from a set of data packages based on the data typesreported from the one or more data sources of the customer user; andreceiving, by the network provider, from the customer user, a selectionof a data package from the provided options of data packages, whereinthe selected data package includes one or more data types, and how andwhen data of the selected data package are to be reported through thewireless uplink.
 2. The method of claim 1, further comprising: reportingdata from the data sources of the customer through the wireless uplinkaccording to the selected data package.
 3. The method of claim 1,further comprising: collecting, by the network provider, statistics ofreporting of data of data packages; adaptively updating the options ofthe data packages provided to the customer based on the collectedstatistics.
 4. The method of claim 1, wherein the options of datapackages provided to the customer are additionally selected from the setof data packages sizes to improve data traffic between the one or moredata sources and the base station.
 5. The method of claim 1, wherein theselected data package includes an identifier, and a template, whereinthe template specifies where different data types are located within thepackage.
 6. The method of claim 5, wherein the selected data packagefurther includes a trigger function that specifies how and when datawithin the selected data package is reported through the wirelessuplink.
 7. The method of claim 6, wherein the trigger function includesone or more of periodic reporting, state change detection reporting, orscheduled reporting of the collected data.
 8. The method of claim 7,wherein the trigger functions are weighted.
 9. The method of claim 1,wherein providing options of data packages to the customer includesselecting options of data packages from the set of data packages sizesadditionally based on behavior of similar types of customers.
 10. Themethod of claim 1, wherein providing options of data packages to thecustomer includes selecting options of data packages from the set ofdata packages sizes additionally based on specific characteristics ofthe user.
 11. The method of claim 1, wherein selected options of thedata package are provided to the one or more data sources through hubprofiles that are generated by the network provider and provided to theone or more data source through the base station.
 12. A data sourcereporting system, comprising: a plurality of data sources, the pluralityof data sources connected through a wireless link to a base station; anetwork server network connected to the base station, the network serveroperative to: receive from a customer user, data types the customer useris to have reported from one or more data sources of the customer user,wherein the reporting is from one or more data sources, and wherein thewireless reporting is through a wireless uplink between the one or moredata sources to a base station; provide options of data packages to thecustomer, wherein the options of data packages are selected from the setof data packages based on the data types reported from the one or moredata sources of the customer user; and receive from the customer user, aselection of a data package from the provided options of data packages,wherein the selected data package includes one or more data types, andhow and when data of the selected data package are to be reportedthrough the wireless uplink.
 13. The system of claim 12, wherein the oneor more data sources are operative to: report data from the data sourcesof the customer through the wireless uplink according to the selecteddata package.
 14. The system of claim 12, wherein the network server isfurther operative to: collect statistics of reporting of data of thedata packages; adaptively update the options of the data packagesprovided to the customer based on the collected statistics.
 15. Thesystem of claim 12, wherein the options of data packages provided to thecustomer are additionally selected from the set of data packages sizesto improve data traffic between the one or more data sources and thebase station.
 16. The system of claim 12, wherein the selected datapackage includes an identifier, and a template, wherein the templatespecifies where different data types are located within the package. 17.The system of claim 16, wherein the selected data package furtherincludes a trigger function that specifies how and when data within theselected data package is reported through the wireless uplink.
 18. Thesystem of claim 17, wherein the trigger function includes one or more ofperiodic reporting, state change detection reporting, or scheduledreporting of the collected data.
 19. The system of claim 18, wherein thetrigger functions are weighted.
 20. The system of claim 12, whereinproviding options of data packages to the customer, wherein the optionsof data packages are selected from the set of data packages sizes, isadditionally based on behavior of similar types of customers.